Creating a Table
The first step in using a Table Widget in your input process is to define a 'Table Source' (look under Processing Objects/Status Checks or under the 'Specifications' pull down menu on the Specifications Tab of Application Design). The Table Source is like a simplified input process that identifies the PCF file to use and which fields to include. For each field you can specify a mask (date and numeric fields) or a size (alpha fields). Via ILF code, you can decide which records to include in the table and pre-select certain records.
Add a new Table Source, identifying the PCF file to use. On the next screen you can list the fields you want included in the table. The order you list them here is the order they will initially be presented to the user. The 'Column' number controls the order of the columns, arrange this however prefer. For each field on the list, you can set either the size or mask, depending on the field type.
There are 4 Event Points associated with the Table Source Process, Start of Process, Post PCF Read, End of Process and File Level Event Points. The Start of Process Event Point executes when the table widget is loaded and the End of Proces Event Point executes when all records have been read. This occurs during the Pre-Display Event Point of the Input process, and may occur more than once depending on how you handle single and double click events (see below). The Post PCF Read event point executes for each record read in the PCF. You can use this to look up data from related fields, exclude records or pre-select records. To exclude a record, set --- INCLUDE RECORD to N. To pre-select a record, set --- SELECT RECORD to Y.
Once you have the Table Source process defined, you are ready to add a Table Widget to an input process. In the Image Editor toolbar, there is a new icon called 'Paint a Table'. Use this tool to draw a rectangle on the image. When you release the mouse, a 'Table Properties' dialog box will appear. This is where you specify the Data Source (the Table Resource process you defined earlier), the invocation type and what options to fire when the user single or double clicks a row (if any). You can also give this widget a name. This will make it easier to tell Table Widgets apart if you are going to have more than one Table Widget on the image.
Once you fill in these details and press Return, the Table Widget will be displayed. The columns and rows will be filled with dummy data to give you a representation of the widget and to help you distinguish the Table Widget from other Widgets on the image.
|